Summary aliasing of search fields #978
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tschaume
requested changes
Apr 10, 2025
There was a problem hiding this comment.
Thanks @esoteric-ephemera! The get_stability function looks good and I think it would be good to release it. Would you mind separating the get_stability and the nelements updates into their separate PRs?
esoteric-ephemera
changed the title
|
Closing this as we're looking into potentially solving this for all low-level query parameters available in the API. |
…nings/exceptions are thrown
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Major changes:
SummaryRester: Allows for searching bynelementsrather thannum_elements, asnelementsis the top-level field in the returnedSummaryDoc. Both kwargs are still supported, but a deprecation warning is thrown ifnum_elementsis specified